Access permissions for users / groups

As we have seen, one way to create a group is to use the Group Registry entry to add a user to a group:

Key Setting
Key 1 User
Key 2 user
Key 3 Group
Value group;group...

If group does not already exist, it is created when user is added to it.

Note: When using the Group Registry entry, a group always comprises at least one user.

In the same way that a group is created when a user is added to it, a group is created when permissions are assigned to it. In this case, a group can be defined as a set of access permissions which can be applied to one or more users. Permissions assigned to a group determine:

  • What modules can be accessed.
  • What tabs in a module are available.
  • Permissions for each field within each tab.
  • Operations that can be performed, e.g. add records, delete records.

Example

To create a set of access permissions that will be applied to all volunteers, you could do the following:

  1. Specify a Table Access Registry entry that defines which modules the Volunteers group will have access to.

    The Volunteers group could be an existing group or a new group. If new, the Volunteers group will be created when this Registry entry is saved.

  2. Specify an Operations Registry entry entry that defines what members of the Volunteers group are able to do on a per table basis (e.g. view, edit, delete, add records, etc.)
  3. For the Volunteers group it might also be required to define which tabs in a module to display using the Tabs | Default Registry entry or even, using the Column Access Registry entry, what permissions members of the group should have on a per field basis.
  4. Add volunteers to the Volunteers group.

    Note: Once a group has been created, users can be added and new permissions can be assigned to it.